Switch Keycloak Integration to NGINX Proxy for Flexible Authentication Setup#718
Merged
Conversation
geso02
changed the title
geso02
changed the title
aaronzi
approved these changes
Apr 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR replaces the former Keycloak plugin-based approach with an NGINX proxy setup.
Previously, a custom Keycloak plugin was required, which tightly coupled the solution to a specific Keycloak version. This made upgrades and maintenance more difficult.
The new approach uses an NGINX proxy to expose Keycloak and all other services under consistent subdomains (e.g., keycloak.basyx.localhost).
Docker services are configured to resolve these subdomains to the Docker host using host-gateway.
As a result, services now access Keycloak via the same URL as specified in the token's issuer claim, allowing Spring Boot's issuer validation to succeed without additional custom plugins.
This simplifies the setup, avoids Keycloak version dependencies, and improves maintainability and portability.